This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Please provide details of any date/time related changes you have encountered. ~Umberto Nongeroson 6.Nov.03 12:44 AM a Web browser Domino Designer All Releases; 6.5; 6.0.3; 6.0.2 CF2; 6.0.2 CF1; 6.0.2; 6.0.1 CF3; 6.0.1 CF2; 6.0.1 CF1; 6.0.1; 6.0All Platforms, Windows 2003, Windows 2000, Windows XP, Windows NT, Windows 95, Windows 98, AIX, Macintosh, Solaris, Linux - RedHat, Linux - SuSE, iSeries, zSeries
Well, there's this one that I reported ages back...
quote
I'm passing a LocalDateTime to the LSGMTTime function (ie LocalDateLime.LSGMTTime), which of course takes the local time zone into account.
Now, it works for almost any time I care to use - except one. 10am. This drove me crazy for ages, until I figured out that it was related to my time zone being GMT +10 (ZE10).
I looked at what was happening in the debugger, and if the time passed to the LSGMTTime function causes the GMT time to be exactly 00:00:00 the function doesn't return a time component at all. Normally, you will get back something like (10/10/2002 02:00:00), with a DateOnly component of "10/10/2002" and a TimeOnly component of "02:00:00"
BUT!
If the GMT time ends up as 00:00:00 then what you get returned is (10/10/2002) with a DateOnly component of "10/10/2002" and a TimeOnly component of ""
This, as you might imagine, causes severe problems...